home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PC Media 4
/
PC MEDIA CD04.iso
/
share
/
os2
/
os2cp210
/
os2copy.doc
< prev
next >
Wrap
Text File
|
1994-05-21
|
31KB
|
403 lines
┌───────────────────────────────────────────────────────────────────────────┐
│ OS2COPY rel. 2.1.02 GA. Copyright (C) 1992-1994: John Ståhle │
│ │
│ What is this ? │
│ │
│ This packet is designed to Copy an ENTIRE OS/2 v. 2.1 GA HPFS or FAT │
│ BootManager system, fully configured, from one partition (drive letter) │
│ to an other (eg. from D: to F:) INCLUDING ALL FILES on the OS/2 │
│ partition, ie. ALSO files not related to the OS/2 system as such. │
│ │
│ This implies that an entire system including all configuration, │
│ installed on one computer can be copied to another if the hard disk │
│ from the second computer is temporarily installed on the first one. │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ Look for these headlines: │
│ │
│ File list This is what it is all about │
│ How to Hands on │
│ Hands on 2. What next ? │
│ Copy FAT -> HPFS Copy HPFS -> FAT (impossible) │
│ Problems A word from the author │
│ Pricing from one computer to another │
├───────────────────────────────────────────────────────────────────────────┤
│ File list: │
│ │
│ All of these are required files: │
│ │
│ OS2Copy.DOC (this file). │
│ OS2Copy.CMD Initiates the copy process. │
│ OS2Copy2.CMD Performs the copy process. │
│ InitEdit.Exe Edits the init files. │
│ YesNo.LNG abbreviations for Yes and No in national language │
│ XCopy.Sw switches for XCOPY │
│ InitEdit.STD list of files to be changed by the program │
│ Not_Copy.Lst list of files NOT to be copied to new system │
│ │
│ BOOT21.HPF Needed if you copy a FAT system to HPFS │
├───────────────────────────────────────────────────────────────────────────┤
│ If your OS/2 system is a 'national language' version (ie. not English) │
│ you +MUST+ edit the file YesNo.LNG Any 7 bit ASCII text editor will do. │
│ │
│ YesNo.LNG abbreviations for Yes and No in your national language │
│ ......................................................................... │
│ │
│ The script will find all .INI files on your system partition; │
│ if, however, some .INI files are located on another partition │
│ (by you, during an installation), you will have to edit the file │
│ InitEdit.STD - any 7 bit ASCII text editor will do. │
│ │
│ If you are copying a national language version of OS/2 (ie. language │
│ other than English) you will probably have to edit this file. │
│ ......................................................................... │
│ │
│ You may also find it necessary to edit the files: │
│ │
│ Not_Copy.Lst list of files NOT to be copied to new system │
│ XCopy.Sw switches for XCOPY (not very likely) │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ All of the above are Copyright (C): │
│ John Ståhle │
│ 289A Buddinge Hovedgade │
│ DK-2880 Bagsværd │
│ Denmark, Europe │
│ Phone +45 44 98 66 18 (voice) │
│ │
│ Internet: john.staahle@dkb.dk or │
│ jost@dkb.dk │
│ RIME OS/2: John Staahle R/O ->1117 │
│ ILINK OS/2: John Staahle │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ This is what it is all about: │
│ │
│ Two co-operating REXX scripts and a co-operating program, │
│ designed to Copy an * OS/2 HPFS or FAT BootManager * system from │
│ one drive letter to another, eg. from D: to E: │
│ │
│ There is no obvious reason why this packet should not work on a │
│ 'OS/2 as only operating system' but this has not yet been tested. │
│ It may even work in a network where you are allowed to repartition and │
│ format a net drive this has not been tested either. │
│ │
│ The .EXE interacts with the two OS2Copy.CMDs, (which also interacts) in │
│ performing the actual editing of OS/2 initfiles (OS2.INI and the like) │
│ to fit on a new partition, creating data files for the scripts, etc. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ How to: │
│ │
│ Prerequisites: │
│ │
│ 1. An installed OS/2 BootManager system │
│ with REXX (part of standard OS/2 installation) │
│ │
│ 2. A partition to Copy to :-) │
│ This partition will become formatted during the procedure │
│ AND it will contain ALL files found on the From system. │
│ The latter implies that the From partition must have │
│ room for these files. │
│ │
│ 3. The files listed as Required in the above Filelist. │
│ │
│ >> All these files MUST reside in the subdirectory from which you │
│ >> start OS2COPY. │
│ >> This subdirectory MUST be included in the PATH statement in your │
│ >> Config.Sys system file +AND+ in your DOS PATH statement in │
│ >> in Autoexec.Bat. │
│ >> It is highly recommended to place this subdirectory entry │
│ >> immediately after "\OS2;" in both of these PATH statements │
│ │
│ Recommended installation procedure: │
│ │
│ Create a subdirectory named O immediately below the root of your │
│ From-Drive (eg. x:\O). │
│ │
│ Copy all files to this subdirectory. │
│ │
│ Include this subdirectory in the two PATH statements in Config.Sys │
│ and Autoexec.Bat, respectively. Reboot after editing these files. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ Hands on: │
│ │
│ >>> First: Make a full backup of your From-drive and of anything you <<< │
│ >>> want to keep on your To drive. <<< │
│ │
│ Next take a look at what is in the following 7 bit ASCII files: │
│ YesNo.LNG, XCopy.Sw and InitEdit.STD │
│ │
│ You +MUST+ edit the file 'YesNo.LNG' if copying a national language │
│ version other than English. Use any 7 bit ASCII text editor. │
│ │
│ If the drive letter in your icon names or paths in the icons' program │
│ name are lower case, I have some bad news for you: │
│ All drive letters in folder and icon names and paths in the icons' │
│ program names MUST be upper case! │
│ │
│ This because it is impossible to know the names of any new WPS classes │
│ that may be registered by a program installation sometime in the future. │
│ I am working on a solution to this - but right now I am out of ideas. │
│ ° <- my head - empty! │
│ │
│ You may need to edit InitEdit.STD - use any 7 bit ASCII text editor - │
│ but unless you have a very non-standard system or applications which │
│ keep hard coded drive information outside the OS*.INI files, I doubt it. │
│ │
│ >>> No other process may be active while the job is running <<< │
│ │
│ Stick to what the program and this documentation file tells you. │
│ │
│ Think while you work. │
│ │
│ Read - actually read - verify and respect the instruction displayed │
│ on your screen while running the two OS2COPY*.CMD-scripts. │
│ │
│ Make sure your OS2*.INI files are in a healthy condition before you │
│ start OS2Copy. Run eg. Henk Kelder's Checkini /C at least twice. │
│ │
│ Open a full screen command line session and type: │
│ │
│ OS2Copy <From Drive> <ToDrive> with or without a trailing ':' │
│ │
│ or just: OS2Copy │
│ │
│ you will be prompted for the missing parameters later in the session │
│ │
│ Samples: │
│ │
│ OS2COPY D │
│ OS2COPY D: F: │
│ OS2COPY D G: │
│ OS2COPY │
│ │
│ Whichever you choose, you are later asked to confirm the FROM and TO │
│ partition (and file system if it differs from your 'to file system). │
│ │
│ Although it is a simple task to make FDISK automatically delete and │
│ create the TO partition, for the sake of safety you are required to do │
│ this manually when FDISK has been started by the script. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ Hands on 2.: │
│ │
│ React to the warnings and follow the instructions displayed on screen. │
│ │
│ WHEN you have made changes using FDISK - │
│ you MUST delete any old partition that may exist where you want the new │
│ system to reside, create a new partition and add it to BootManager │
│ - or you will have to restart the procedure from scratch. │
│ │
│ Upon leaving FDISK you are told to press CTRL ALT DEL Do so. │
│ Do +NOT+ press the RESET button, FDISK has not finished writing │
│ the new partion table yet. │
│ │
│ When your system reboots, the OS2Copy2 is automatically called from a │
│ temporary STARTUP.CMD file in your <From Drive> root directory. │
│ │
│ When copying is finished, you MAY have to copy your original STARTUP.CMD│
│ (now named STARTUP.@#@) back into STARTUP.CMD. │
│ I have never experienced this myself, but I know (inside info '-)) │
│ that the automatic restore of STARTUP.CMD does not always work. │
│ │
│ A backup of the original <From Drive> init files, Config.Sys and │
│ Autoexec.Bat are left in a subdirectory named <To Drive>\<From Drive> │
│ (eg. F:\D ). │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ What next ? │
│ │
│ If everything went smooth, your computer will boot when copy is complete. │
│ │
│ The first time you boot from the newly created system, │
│ sometimes only a skeleton WPS shows up. │
│ │
│ How do you recover ? │
│ ┌───────────────────────────────────────────────────────────────────┐ │
│ │ >>> !!! Reboot IMMEDIATELY using Control+Alt+Del !!! <<< │ │
│ │ │ │
│ │ !!! Do NOT perform an orderly shut down !!! │ │
│ │ !!! Do NOT make any changes to the WPS !!! │ │
│ │ !!! Do NOT press the RESET button !!! │ │
│ │ !!! Do NOT power off !!! │ │
│ │ │ │
│ │ >>> !!! Reboot IMMEDIATELY using Control+Alt+Del !!! <<< │ │
│ └───────────────────────────────────────────────────────────────────┘ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ Problems: │
│ │
│ Make sure your OS2*.INI files are in a healthy condition. │
│ Run eg. Henk Kelder's Checkini /C twice or more. │
├───────────────────────────────────────────────────────────────────────────┤
│ One problem I have had reported is that if in your Autoexec.Bat you │
│ have the statement Comspec= or SET Comspec= the Initedit.Exe will not │
│ work correctly. Comment it out like this: ::Comspec= or ::SET Comspec= │
│ until you have finished copying (:: is the same as Rem, but quicker) │
│ │
│ Normally you do not need the Comspec statement, a Shell= statement in │
│ in Config.Sys is sufficient. │
├───────────────────────────────────────────────────────────────────────────┤
│ If the the OS/2 copy does not show a WPS when you boot from it, │
│ check your original WPS. │
│ All drive letters in folder and icon names and paths in the icons' │
│ program names MUST be upper case! │
├───────────────────────────────────────────────────────────────────────────┤
│ There used to be problems, if you copied a HPFS system FROM E: K: or L: │
│ The problem was located to the line │
│ IFS=x:\OS2\HPFS.IFS /CACHE: /CRECL: /AUTOCHECK: │
│ ^^ ^^ ^^ │
│ AFAIK this has been fixed in the present release. │
├───────────────────────────────────────────────────────────────────────────┤
│ If you copy from a system with high resolution monitor + video card │
│ to a system with low resolution monitor + video card or from color to │
│ mono (black and white) you are in trouble. │
│ Oh well, not really: │
│ Boot from floppy. │
│ Go to new system drive, CD OS2 │
│ Have Display Driver diskettes ready. │
│ Run SetVGA.CMD │
│ That's it! │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ Copy FAT -> HPFS │
│ │
│ It is possible to copy a FAT filesystem OS/2 to a HPFS filesystem OS/2. │
│ │
│ This, however, is NOT an ideal copy, since a number of subdirectories │
│ and files have different names under FAT (8.3 names) and HPFS (254 char. │
│ names). Many HPFS subdirectory names also have embedded spaces. │
│ Still, you can live with it, the new system will work as HPFS in every │
│ other aspect. │
│ │
│ IMPORTANT !! │
│ If you have not already installed support for HPFS, you must do this │
│ using System Setup -> Selective Install -> High Performance file system. │
│ │
│ You may also have to insert (AFTER installation of HPFS support), │
│ as the first line in your Config.Sys: │
│ IFS=<sysdrive>:\OS2\HPFS.IFS /CACHE:512 /CRECL:4 /AUTOCHECK:<drive> │
│ │
│ <sysdrive> is your present OS/2 system drive. │
│ <drive> is the intended HPFS drive (no trailing colon eg. /AUTOCHECK:F ) │
├───────────────────────────────────────────────────────────────────────────┤
│ Not Copy HPFS -> FAT │
│ │
│ It is NOT possible to copy a HPFS system to a FAT system, for the reasons │
│ given above (subdir and file names). │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ Copying an entire system including all configuration │
│ from one computer to another: │
│ │
│ Install and configure OS/2 on hard disk 2 (often D:) on From-computer. │
│ │
│ Physically install the hard disk to transfer to as disk 1 (C:) │
│ │
│ Begin installing OS/2 on hard disk 1 (C:) using the OS/2 installation │
│ diskettes. │
│ Configure the C: partition as PRIMARY (using FDISK). │
│ Insert the configured OS/2 system and the From-drive into BootManager. │
│ Abort when the C: disk has been formatted and boot manager is installed.│
│ │
│ Boot from D:. │
│ OS2Copy D: C: │
│ Remove hard disk 1 and insert it in To-computer. │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ │
│ Legal section: │
│ │
│ The OS2COPY packet has been thoroughly tested and shown to work │
│ flawlessly on a number of different systems. │
│ │
│ It is, however, distributed * AS IS *. │
│ │
│ NO responsibility or any other obligation you can ever think of, │
│ shall be assumed, honored or anything else. │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ This Ståhle (C) software may NOT be used for production by a business, │
│ government agency or institution without payment of a license fee. │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Public Domain 10 copy version. │
│ │
│ If and * ONLY IF * this packet is used on a private and │
│ personally owned computer, it is placed in the Public Domain. │
│ │
│ The Public Domain version will be able to perform 10 copies. │
│ │
│ If you find the software of use to your company etc. and want to │
│ purchase it, you must order and pay for a number of copies. │
│ │
│ A limited right to TEST this software is granted +anyone+ for │
│ * A TOTAL OF NO MORE THAN 10 system transfers * │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Pricing: │
│ │
│ As mentioned above, OS2COPY is freeware for the first 10 copies. │
│ │
│ 50 copy version: US$ 100.00 + air mail postage (US$ 5-10). │
│ 100 copy version: US$ 150.00 + air mail postage(US$ 5-10). │
│ 500 copy version: US$ 500.00, no postage. │
│ No limit version: US$ 1,000.00, no postage. │
│ (A 'No limit' version which is "fully" automated │
│ ie. limiting manual work to little more than starting and rebooting │
│ the computer, may be ordered at no extra charge). │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ A word from the author: │
│ │
│ It may seem a kludge that names of files to be edited and subdirectory │
│ name converting tables etc. are placed in ASCII files instead of being │
│ hardcoded into program and scripts or being placed in some fancy │
│ binary files. │
│ It may also seem a kludge that so much of the code is written in REXX. │
│ │
│ This approach, however, enables you to │
│ (hopefully) keep pace with future updates of OS/2, without having to │
│ buy updates of this packet │
│ (not that I don't want to sell updates, but let's be reasonable). │
│ and to │
│ add init files related to programs, which create their own init files │
│ with "hard coded" partition information, instead of using OS2.INI │
│ and to │
│ add binary files, eg. programs, with "hard coded" drive letters │
│ and to │
│ add text files like Config.sys and ATM.INI including drive letters │
│ and to │
│ use this packet with the different national language versions of OS/2 │
│ and to │
│ use this packet even if you have changed the standard names of subdirs.│
│ │
│ Regards, John Ståhle │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ That's all. │
└───────────────────────────────────────────────────────────────────────────┘